Additional documents of interest
- Successful Business Continuity - Part 1 - Users and Groups
-
This article was published in the April 2005 issue of
AIX Update magazine
and discusses system administration needs and requirements oriented
around users and groups. The overall emphasis of this series of
articles is for implementation of enterprise wide unique identifiers
for a variety of parameters, such as user names, group names, UID and
GID numbers.
- Successful Business Continuity - Part 2 - Machine and Host Names
-
This article was published in the May 2005 issue of
AIX Update magazine
and discusses naming structures for machines, systems, adapters, and
aliases. The overall emphasis of this series of articles is for
implementation of enterprise wide unique identifiers for a variety of
parameters.
- Successful Business Continuity - Part 3 - Volume Names
-
This article was published in the December 2005 issue of
AIX Update magazine
and discusses naming structures for volume groups, logical volumes, log
logical volumes, directory mount points, etc. The overall emphasis of
this series of articles is for implementation of enterprise wide unique
identifiers for a variety of parameters.
- Successful Business Continuity - Part 4 - MQ Series, Startup/Shutdown Scripts, Error Processing
-
This article was published in the April 2006 issue of
AIX Update magazine
and discusses how to implement AIX in an environment dedicated to
business continuity. The topic of this article is the assignment of MQ
Series queue names and aliases, resource group startup and shutdown
script names (Application startup/shutdown script names), error logging,
and error notification.
- Successful Business Continuity - Part 5 - Miscellaneous topics
-
This article was published in the August 2006 issue of
AIX Update magazine
and discusses how to implement AIX in an environment dedicated to
business continuity. A variety of topics is discussed in this article
including automated documentation generation and management.
- Automated Microcode Management System
-
One of the most difficult administration tasks in an AIX environment is
attempting to keep the firmware and microcode up-to-date. Mt Xia has
devised an automated method of gathering the Microcode information,
determining which microcode needs to be updated, generating reports, and
uploading the required microcode updates to each individual system.
- Calculating the size of a Virtual Processor
-
This document describes the algorithms used to calculate the size of a
virtual processor when using shared processors in an LPAR. The IBM
documentation describes how to calculate CPU utilization, NOT how to
size for configuration, this document clarifies this process. A
description of the HMC input fields for the processor tab is included.
- Basics of Partition Load Manager Setup
-
This presentation was provided by Ron Barker from IBM regarding the PLM Basic
setup.
- ppt
- pdf
|
 |
 |
 |
 |
File System Mount Point Directory Name Standards
This document describes the standards for assigning AIX filesystem
mount point (MtPt) directory names. A single standard has been developed
for use in standalone, High Availability, and Disaster Recovery
environments. This filesystem mount point directory naming standard
provides the mechanism to assign enterprise wide unique names to all AIX
filesystem mount point directory's and will eliminate naming conflicts
in the event of a manual or automated failover, or if multiple instances
of an application are running on a single server.
To assign enterprise wide unique LV names, the system administrator
must first define the Resource Groups,
Volume Groups, and
Logical Volumes. Once these have been defined, the filesystem mount
point directory names can be assigned. Typically a filesystem mount
point is required for each logical volume, therefore the mount point can
usually be based on the logical volume name, or at a minimum the
resource group name.
To define a filesystem mount point directory name, obtain the 8 character resource group name, then
depending upon the applications filesystem requirements, use the RG name
as the mount point, or add sub-directories to make it enterprise wide
unique.
The filesystem mount point directory name shall consist of at least
8 characters, but may be of a variable length:
/ + ApplicationCode + Environment + Function + Company + Sequence ID + ( LV Sequence ID or Directory Structure )
3 char + 1 char + 1 char + 2 char + 1 char + 4 or more char
As an example, a resource group named "egaapmx0", may have multiple
file systems associated with it:
RG Name
Component
|
Optional
Logical Volume
Sequence ID
|
Optional
Sub-Directories
|
Filesystem
Mount Point
|
|
egaapmx0
|
|
db2_08_01/bin
|
/egaapmx0/db2_08_01/bin
|
|
egaapmx0
|
|
db2_08_01/data
|
/egaapmx0/db2_08_01/data
|
|
egaapmx1
|
mq01
|
|
/egaapmx1mq01
|
|
egaapmx1
|
mq02
|
|
/egaapmx1mq02
|
|
egaapmx1
|
mq03
|
|
/egaapmx1mq03
|
|
 |
 |
 |
 |
|
|
